home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
system
/
dosmax21.zip
/
DOSMAX.DOC
next >
Wrap
Text File
|
1993-06-01
|
34KB
|
740 lines
================================================================================
DOSMAX.EXE : Ver. 2.1, Copyright (1992,93) by Philip B. Gardner
================================================================================
DOSMAX.EXE is a device driver which will maximize the use of low memory
by moving MS-DOS 3.1 and above system data to upper memory blocks provided
by your upper memory manager. It is not necessary to use any other
programs to create upper memory data types like FILES, BUFFERS, FCBS,
or LASTDRIV from Quarterdeck's QEMM386. These data types are referred
to as "sub-segments" in the rest of this document.
In addition, if you are a DOS 5.0 or above user and are loading DOS high,
then DOSMAX can prevent DOS from loading into the HMA and move the DOS
kernel to an upper memory block. This improves performance and allows
programs which use the HMA more efficiently to utilize the HMA instead.
Such programs include Microsoft WINDOWS and Quarterdeck's DESQVIEW.
Version 2.0 now requires the device driver STOPMAX.SYS to prevent DOS from
loading into the HMA (see STOPMAX.DOC). The DOSMAX driver then moves
the kernel into upper memory at the proper time.
DOSMAX can also move a portion of COMMAND.COM into an upper memory block
instead of the HMA. This feature recovers space in low memory which is
available when DOS is in the HMA. Version 2.0 now requires the /C+ switch
to enable this feature rather than /A0 to disable it.
Support is automatically provided for Microsoft WINDOWS 3.x so that all
FILES in your CONFIG.SYS can be loaded high. Normally this would prevent
WINDOWS from running, but the problem is circumvented. Version 2.0 has
changed the support algorithum significantly, see /W+ option below.
Support is provided for:
* moving all DOS's sub-segments types into upper memory
* moving DOS's SYSTEM block (kernel) into upper memory (STOPMAX installed)
* supporting WINDOWS start-up even if all FILES= are in upper memory
* moving a portion of COMMAND.COM into high memory instead of the HMA
* DOS Versions 3.1 - 3.31, DOS 4.x, DOS 5.x, and DOS 6.x (or better?)
DOSMAX automatically moves all the data that can be moved dependent only
upon the availability of upper memory. It will automatically stop moving
data when it determines that memory would be fragmented if the move were
completed.
Finally, a command line mode is provided to control Windows support, and
check and report on the status of the high memory area reserved for
COMMAND.COM. Version 2.0 moves the Master Environment moving feature
into a separate program, see ENVIMAX.DOC.
================================================================================
(Requirements)::
* Requires MS-DOS Version 3.10 or better
* Now supports DR-DOS 6.0
================================================================================
(Installation)::
(CONFIG.SYS)::
Installation of DOSMAX.EXE requires modifying the contents of
your CONFIG.SYS file.
(Generic Configuration)::
This configuration should work and be the most efficient in 95%
of all configurations. For a few real world examples see
EXAMPLES.DOC
DOS=HIGH[,UMB] (DOS 5.x or 6.x only)
REM DEVICE=STOPMAX.SYS [options] (Stops kernel from loading in HMA)
DEVICE=(xms/umb memory manager)
DEVICE=DOSMAX.EXE [options] (DOSMAX loads high automatically)
SHELL=SHELLMAX.COM COMMAND.COM /P
BUFFERS=20
FILES=40
LASTDRIVE=Z
For DESQView users, it is recommended that the DEVICE=STOPMAX.SYS is
installed. This enables DOSMAX's kernel moving feature.
DOS 5.x and 6.x users should configure DOS to load high into the
HMA. The UMB parameter is optional, since both DOS 5.x and 6.x
upper memory management and XMS upper memory blocks are supported.
DOS=HIGH[,[UMB][NOUMB]] (Both DOS UMB's and XMS UMB's supported)
Insert a DEVICE= line for DOSMAX.EXE in your config.sys. Ver. 1.5
of DOSMAX recommended that DOSMAX be loaded before the XMS and UMB
memory manager, but DOSMAX should now be loaded after the XMS manager
(DOSMAX will automatically load itself high if UMB's are available
or you may use your memory manager's device loader). Version 1.7
provided another way to ensure that the DOS 5.0 or above kernel
is moved into a UMB by DOSMAX. The driver STOPMAX.SYS is inserted
"before" the XMS manager and DOSMAX is inserted "after" the XMS
manager (see STOPMAX.DOC).
Version 2.0 now requires that STOPMAX.SYS is used to stop DOS from
loading into the HMA, support for /B+,/I+ and /V+ have been removed
from DOSMAX.EXE because these options caused confusion.
Version 2.0 now requires /C+ to enable the upper memory support
option for COMMAND.COM. This option was provided by default in
earlier versions and was disabled with /A0. Normally you will
want to use SHELLMAX.COM to load all of COMMAND.COM into upper
memory (see SHELLMAX.DOC). The /A0 option also caused confusion.
REM DEVICE=STOPMAX.SYS [options]
DEVICE=(Memory Manager)
DEVICE=DOSMAX.EXE [/C:+][other options]
One advantage of using DOSMAX.EXE, is that the STACKS=, BUFFERS=,
FCBS=, FILES=, and LASTDRIVE= parameters may be configured normally.
STACKS=9,256 (or =0,0 or default 9,128...etc...)
BUFFERS=XX[,YY] (XX = # of buffers, YY = lookahead cache)
FCBS=XX,YY (XX = # of FCBS, YY = # of protected FCBS)
FILES=NN (NN = # of system files)
LASTDRIVE=Z ( Z = Last reserved drive)
Version 2.0 of DOSMAX now allows INSTALL=, you no longer have to
remove these statements from your CONFIG.SYS.
By default, DOSMAX.EXE Version 2.0 will not generate report messages
for each successful operation or event, unless you enable the report
with /R+. You must also use /P+ to pause after this report. Use
/R+ and /P+ until you are satisfied with the configuration then
remove these switches.
DEVICE=DOSMAX.EXE /R+ /P+
or DEVICE=DOSMAX.EXE /REPORT:+ /PAUSE:+
(AUTOEXEC.BAT)::
It is not necessary to modify the contents of AUTOEXEC.BAT, but
since DOS data creators like FILES and BUFFERS are no longer
required, it is recommended that these lines be removed
REM BUFFERS=XX (Remove FILE and BUFFER creator TSR's)
REM FILES=NN
(From the Command Line)::
By default, DOSMAX.EXE, invoked from the command line, will generate
a message for each successful operation or event. The display will
not pause in the command line mode unless the /P+ switch is used.
After you are satisfied with the configuration and you want to disable
the REPORT feature, use:
DOSMAX.EXE /R-
All switch options and possible messages for DOSMAX are detailed
below:
(Loading DOSMAX High)::
You may load DOSMAX high with your high memory loader, but DOSMAX
will load itself high if upper memory is available. To prevent
DOSMAX from loading itself high, use /X- or load it before the
memory manager is installed.
(Moving the DOS kernel into a UMB)::
DOSMAX to move the DOS 5.0 or above kernel to a UMB, then DOS
must not be in the HMA when DOSMAX loads. If you desire to stop
the kernel from moving into the HMA, then STOPMAX must be loaded
before the xms/umb memory manager, so that the DOS kernel is not
high when DOSMAX initializes. If DOS is already in the HMA (not
using STOPMAX), then Verision 2.0 now detects this condit